Method for delivering messages in a wireless communications system using the same protocol for all types of messages

ABSTRACT

A method and a wireless telecommunications system, a message service center and a mobile station implementing the method for transmitting messages between a mobile station and a second party. The method of the invention includes delivering messages irrespective of the presentation thereof: delivering messages through the same message service center irrespective of the content type and employing the same protocol between the terminal and the message service center for all messages. The content type indicates the presentation of the message contents which may include test, speech, images, video images or various combinations thereof.

This application is the national phase of international applicationPCT/FI99/00518 filed Jun. 14, 1999 which designated the U.S., and thatinternational application was published under PCT Article 21(2) inEnglish.

BACKGROUND OF THE INVENTION

The invention relates to a messaging service in a wirelesstelecommunications system enabling the transmission of various messagetypes, such as text, images, speech, video images or other data orcombinations thereof from a sender to a recipient using the sametransmission mechanism, and more particularly to a messaging service ina mobile communications system.

Mobile communications systems have been developed since a need hasarisen for people to freely move away from fixed terminals withoutmaking it more difficult to reach them. Services offered through mobilestations have improved with the mobile communications systems. Variousnew forms of services are currently being created for what are known asthe third generation mobile communications systems, such as theUniversal Mobile Telecommunications System (UMTS) and IMT-2000(International Mobile Telecommunications 2000), and for current mobilecommunications systems, such as the Pan-European mobile communicationssystem GSM (Global System for Mobile communications), including theGeneral Packet Radio Service (GPRS) currently being standardized in theGSM phase 2+ in ETSI (European Telecommunications Standard Institute).

The GPRS service is used for providing packet data transmission betweenmobile data terminals and external data networks, since the GSM networkfunctions as an access network. One of the conditions set for the GPRSservice is that it must operate together with various external datanetworks, such as the Internet or X.25 networks. The GPRS service andthe GSM network should therefore be able to serve all users,irrespective of the type of data networks they wish to be connected tothrough the GSM network. This means that the GSM network and GPRSservice must support and process different network addressing methodsand data packet formats. The data packet processing also comprisesrouting of packets in a packet radio network. In addition, the usersshould be able to roam from their home GPRS network to a visited GPRSnetwork, whose operator backbone network may support a differentprotocol (for example CLNP) than the home network (for example X.25).

Known messaging services include short message services and voice mailservices. Text messages can be sent as short messages. Voice mailservices are in general answering services transmitting voice messages.However, a drawback is that neither of said services enable thetransmission of images or video images, not to mention the transmissionof messages including multimedia. Another problem is that a text messageis sent to a different service centre than a voice message. Stillanother problem is that the size, or the duration, of at least a voicemessage is limited.

BRIEF DESCRIPTION OF THE INVENTION

It is an object of the invention to provide a method and an apparatusimplementing the method so as to solve the above problems. The objectsof the invention are achieved with the method, system, service centreand mobile station, characterized by what is disclosed in theindependent claims. The preferred embodiments of the invention are thesubject of the dependent claims.

The invention is based on the idea to concentrate the transmission ofmessaging services into one logical service centre in such a manner thata message can be sent from a sender to a recipient through the servicecentre irrespective of the contents or size of the message. The messagemay contain text, images, speech, video images, other data orcombinations thereof. From hereafter such a message will be referred toas a multimedia message. Here the term multimedia message refers to thecontent type of the message, meaning that the contents of the messagecan be represented in a number of ways. The contents may include onlytext, only speech, text and images, video images and speech, videoimages including speech and text.

The invention provides the advantage that different types of messagescan be delivered to the recipient through one service centre. Anotheradvantage of the invention is that messages including images, videoimages and multimedia can be sent to a mobile station. A furtheradvantage of the invention is that the size of the multimedia messagesdoes not have to be restricted in any way.

In a preferred embodiment of the invention only a message fulfillingcertain conditions is sent directly to the terminal, i.e. to therecipient. This embodiment provides the advantage that the recipient candecide when he/she wants to receive a multimedia message. This is aparticularly useful property especially when large multimedia messagesare concerned.

In another preferred embodiment of the invention the user of the mobilestation can update the conditions of a direct delivery. This embodimentalso provides the advantage that the recipient can decide what kind ofmessages he/she wants to receive as direct deliveries.

In a further preferred embodiment of the invention the properties of theterminal are employed in the direct delivery conditions. This embodimentprovides the advantage that such messages are not delivered to therecipient that he/she cannot open with a terminal in use.

In another preferred embodiment of the invention the multimedia messageservice centre changes the message contents into a mode supported by theterminal. This embodiment also provides the advantage that the senderdoes not have to know, for example, what kind of image coding therecipient terminal supports. Furthermore, the recipient receivesmessages that his/her terminal supports.

In a further preferred embodiment of the invention the multimediamessage service centre packs the message contents. This embodiment hasthe advantage that the amount of data to be transferred can beminimized, thus saving network resources.

In a still further preferred embodiment of the invention the multimediamessage service centre selects a delivery route for the message based oncertain conditions. This embodiment also provides the advantage that themessage is transferred by employing the best possible route taking thecontents into account.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following the invention will be described in greater detail inconnection with the preferred embodiments with reference to theaccompanying drawings; in which

FIG. 1 illustrates a telecommunications system of a first preferredembodiment,

FIG. 2 shows signalling associated with MMS-context activation,

FIGS. 3, 4 and 5 show signalling according to a protocol needed fortransferring a multimedia message in a first preferred embodiment,

FIG. 6 is a flow chart showing how a multimedia message service centreoperates in a first preferred embodiment,

FIG. 7 illustrates a multimedia message service centre of the invention,and

FIG. 8 illustrates a mobile station of the invention.

DETAILED DESCRIPTION OF THE INVENTION

In the following the preferred embodiments of the invention will bedescribed by means of GPRS packet radio networks without restricting theinvention to such a particular packet radio system. The invention can beapplied to all wireless data transmission networks that support at leasttwo different message types. In particular, the invention can be appliedto what are known as the third generation mobile communications systemsUMTS and IMT-2000 supporting, for example, the transmission of videoimages. It should be noted that a packet radio network offers only aphysical connection between a multimedia message service centre and aservice recipient, and the exact functionality and structure thereof arenot significant for the invention. The definitions concerning mobilecommunications systems in general and the GPRS service in particularimprove rapidly. Placing different functionalities into network elementsmay vary, which is why all words and expressions should be interpretedbroadly, as they are intended to describe not to restrict the invention.

FIG. 1 illustrates a GPRS packet radio service implemented in the GSMsystem, where the GSM network offers circuit-switched data transmission,whereas the GPRS service offers packet-switched data transmission. Asfor the invention, FIG. 1 shows the most important elements andfunctions.

The basic structure of the GSM network comprises two parts, a basestation subsystem (BSS) and a network subsystem (NSS). The base stationsubsystem BSS and mobile stations MS communicate through radioconnections 1. The network subsystem comprises at least one mobileswitching centre MSC, at least one visitor location register VLR and ahome location register HLR. The function of the mobile switching centreis to switch calls including at least one mobile station MS. Some mobileswitching centres MSC are connected to other telecommunicationsnetworks, such as a public switched telephone network 5 (PSTN),including transmission functionalities for switching calls to and fromthese networks. The visitor location register VLR is generally connectedto a mobile switching centre MSC but it may also serve several centres.When a mobile station MS is active in the GSM network (it has registeredinto the network and can start or receive a call) most of the subscriberdata concerning the mobile station MS in the home location register HLRis loaded (copied) into the visitor location register VLR of the mobileswitching centre MSC, in which area the mobile station MS is. For a moredetailed description of the GSM system reference is made to the ETSI/GSMrecommendations and to the book “The GSM System for Mobilecommunications”, M. Mouly and M. Pautet, Palaiseau, France, 1992,ISBN:2-9507190-07-7.

In FIG. 1 the GPRS service connected to the GSM network comprises oneGPRS network having one serving GPRS support node SGSN and one GPRSgateway support node GGSN. These different support nodes SGSN and GGSNare interconnected by an intra-operator backbone network 2 (GPRSBackbone). It should be understood that the GPRS network may compriseany number of support nodes and gateway support nodes.

The serving GPRS support node SGSN is a node serving a mobile stationMS. Each support node SGSN manages the packet data service in the areaof one or more cells in a cellular packet radio network. For thispurpose, each support node SGSN is connected to a particular local partof the GSM mobile communications system. This connection is typicallymade to the base station subsystem BSS, and generally to a base stationcontroller in the BSS. The mobile station MS in a cell communicates witha base station across a radio interface 1 and further through the basestation controller with the support node SGSN to whose service area thecell belongs. In principle, the mobile communications network betweenthe support node SGSN and the mobile station MS only transmits packetsbetween the two. For this purpose, the mobile communications networkoffers transmission of packet-switched data packets between the mobilestation MS and the serving support node SGSN.

The GPRS gateway support node GGSN connects the GPRS network of theoperator with other GPRS services of the operators and with datanetworks 5, such as the IP network (Internet, Intranet) or X.25 network.The GGSN comprises routing information of GPRS subscribers, or the SGSNaddresses. The SGSN and GGSN functions can be connected to the samephysical node.

The home location register HLR of the GSM network includes the GPRSsubscriber data, the telephone number MSISDN (Mobile Subscriberinternational ISDN number) of the mobile station subscriber and therouting information connecting the international mobile subscriberidentity IMSI of the subscriber with said data. The GPRS subscriber dataincludes PDP-contexts and default GGSNs and addresses thereof, forexample as IP addresses. In addition, the home location register HLR ofthe invention can maintain an address list for each subscriber in itsregisters, the address list comprising the address of the multimediamessage service centre where a multimedia message is waiting fordelivery to the mobile station. The list is maintained in the same wayas the address list of short message service centres SMSC. Furthermore,the HLR can alert the multimedia message service centre MMSC in the sameway as the short message service centre, when the subscriber registersinto the network. Hence, the HLR “considers” the multimedia messageservice centre MMSC as merely a new network element and is able toperform the functions required by the invention by employing currentroutines. Only additional memory is needed. The home location registerHLR of a roaming mobile station MS can be placed in another mobilecommunications network than the serving SGSN.

An intra-operator backbone network 2 interconnecting the operatorequipment SGSN and GGSN can be implemented, for example, by a localnetwork, such as the IP network. It should be noted that it is alsopossible to implement the operator GPRS network without theintra-operator network, for example by implementing all the features inone computer.

An inter-operator GPRS backbone network 3 is a data network throughwhich the gateway support nodes GGSN of different operators cancommunicate with one another.

Here a mobile station MS generally refers to an entity composed of amobile station subscriber and an actual terminal. The terminal can beany terminal that is able to communicate in a mobile communicationssystem or a combination of several terminals, like a multimediacomputer, to which, for example, a card phone manufactured by Nokia isconnected in order to establish a mobile-like connection. The subscriberis identified from a subscriber identification module SIM detachablyconnected to the terminal. As the identification module is detachable,the subscriber may change terminals and use a terminal that is bestsuitable for each purpose. The mobile station of the invention isdescribed in greater detail below in FIG. 8.

For short message service the system comprises a short message servicecentre SMSC and a short message service gateway SMSGW. The short messageservice gateway SMSGW transmits short messages to and from a mobilestation.

The system of the invention comprises a multimedia message servicecentre MMSC for multimedia message service MMS. The multimedia messageservice centre MMSC is not necessarily one entity but can be composed offunctionalities decentralized into different units. Hereafter themultimedia message service centre MMSC will, however, for clarity betreated as one entity. The MMSC forwards multimedia messages and storesand resends multimedia messages, which have not been delivered. Themultimedia message service centre MMSC can preferably receive amultimedia message to be delivered to a mobile station through anynetwork. The operator can, if he/she desires, restrict such deliveringnetworks to certain network types only, for example to public andprivate IP networks. The operation, structure and interfaces of amultimedia message service centre will be explained below in FIG. 7.FIG. 1 shows a first preferred embodiment of the invention, where themultimedia message service centre MMSC is directly connected to theintra-operator backbone network 2, in which case it functions also as aGPRS gateway support node. In the first preferred embodiment themultimedia message service centre communicates with the home locationregister HLR and the short message service centre SMSC, a data network 4and the public switched telephone network 5. These connections areeither direct signalling connections or signalling connectionsimplemented through an internal network.

In a mobile communications network the home and visitor locationregisters are used substantially in the same way for routing multimediamessages as for routing calls or short messages. In the first preferredembodiment the multimedia message route is generally the following:multimedia message service centre MMSC—intra-operator backbone network2—serving support node SGSN—base station subsystem BSS—mobile stationMS. A GPRS air interface is then used as a radio interface. Airinterfaces, such as W-CDMA, defined in the third generation systems canalso be used as the radio interface. The advantage of this embodiment isthe rapid delivery of the multimedia message. Another advantage is thatthe solution does not load the circuit-switched network part.

The solution according to the first preferred embodiment can alsosupport the loading of the multimedia message to the mobile stationusing circuit switching, in which case the delivery route is, forexample, the following: multimedia message service centre MMSC—publicswitched telephone network 5—mobile services centre MSCNLR—base stationsubsystem BSS mobile station MS. The GSM air interface or air interfacesdefined in the third generation systems, such as EDGE, are then used asthe radio interface.

In a second preferred embodiment (not shown in the Figure) themultimedia message service centre is connected to the short messageservice gateway SMSGW. The multimedia message service centrecommunicates with the data networks 4 and possibly with the publicswitched telephone network 5. In the second preferred embodiment themultimedia message route is in general the following: multimedia messageservice centre MMSC—short message service gateway SMSGW—serving supportnode SGSN—base station subsystem BSS—mobile station MS. An advantagewith this solution is that message transmission can utilize the currentconcatenation of short messages and no major changes need to be made tothe system. Another advantage with the solution is that multimediamessages can be delivered as normal short messages through a mobileswitching centre MSC, if no GPRS connection is available. However, thetransmission of messages is then considerably slower than when using aGPRS connection. In the solutions according to the second preferredembodiment the multimedia message service centre MMSC can be integratedto a short message service centre SMSC.

In a third preferred embodiment (not shown in the Figure) the multimediamessage service centre MMSC is connected to a gateway support node GGSNthrough the intra-operator backbone network 2 or the inter-operatorbackbone network 3. The multimedia message service centre communicateswith the data networks 4 and possibly with the public switched telephonenetwork 5. In the third preferred embodiment the multimedia messageroute is in general the following: multimedia message service centreMMSC GPRS gateway support node GGSN—serving support node SGSN—basestation subsystem BSS—mobile station MS. The solution provides theadvantages that a multimedia message can be delivered rapidly, thecircuit-switched network is not loaded, multimedia messages can also bedelivered to fixed IP addresses and the multimedia message servicecentre does not necessarily need an SS7 protocol stack. In addition, thenetwork does not require new interfaces.

A multimedia message entity MME can be any means enabling messages to besent and/or received. The most simple MME can transmit only, forexample, speech or text, whereas a complex MME can transmit video imagesincluding text and speech. The MME can be a mobile station, an entityconnected directly to the multimedia message service centre or anapplication sending a multimedia message through the data network 4. Thesending multimedia message entity and the users thereof must beidentifiable as accurately as the billing requires in the embodiments inwhich the sender pays for the transmission of the message.

When the mobile station MS makes attach to the GPRS network, i.e. inconnection with a GPRS Attach procedure, the SGSN forms a mobilitymanagement context (MM-context) comprising information associated with,for example, the mobility and safety of a mobile station MS.Correspondingly, in connection with a PDP activating procedure the SGSNforms a PDP-context which is used for routing purposes within the GPRSnetwork with the GGSN that the GPRS subscriber employs. Since themultimedia message service centre MMSC operates in the first and secondpreferred embodiments as the gateway support node GGSN for themultimedia messages, a context can correspondingly be activated betweenthe mobile station and the multimedia message service centre, what canbe called a multimedia message service context (MMS-context). When saidcontext is activated the mobile station can receive and send multimediamessages. An alternative for activating the MMS-context is that the MMSCsends a multimedia message without separately activating the context.Then the MMSC requests for routing instructions from the home locationregister HLR and upon reception thereof sends a particular message (MMSDatagram) to the SGSN, which finds a user within the area on the basisof the MSISDN number or the IMSI and sends said message over the radiointerface to the mobile station MS. The mobile station MS acknowledgesthe message by sending a reply message (MMS Datagram Acknowledge). Thisalternative solution requires that the MMSC, SGSN and MS are constantlyready to receive multimedia messages, even if a particular context isnot activated. In addition, new datagrams (messages resembling thesignalling messages) have to be defined into GTP (GPRS TunnelingProtocol) and SNDCP (Subnetwork Convergence Protocol) protocols.Furthermore, an NSAPI value informing the recipient that a multimediamessage is concerned has to be allocated for the transmission ofmultimedia messages. A tunnel identifier (TID) used in the GTP protocolcan be composed of the user IMSI and the NSAPI value allocated tomultimedia messages. Based on this information the SGSN knows that amultimedia message is concerned and finds the user even if it does notknow the MSISDN number thereof. When the MS wishes to send a multimediamessage, it uses corresponding messages in the uplink direction. TheMMSC can be identified using an APN or in some other way.

The multimedia message context activation is carried out, for example,using the signalling shown in FIG. 2, where, the mobile station MS sendsan activate PDP-context request (ActivatePDPContextRequest) to theserving support node SGSN in message 2-1. The message includes at leastan access point name APN allowing to identify the multimedia messageservice centre and an indication of the desire to activate a multimediacontext. Other means than the APN for indicating an address can also beused as the multimedia message service centre address. What is essentialis that the multimedia message service centre is identified in some way.In addition, message 2-1 may include information about how much memorythe mobile station has available for multimedia messages, what kind ofdata the mobile station supports (text, images, speech) and thepresentation format thereof. Furthermore, the message may include valuesfor some condition parameters. A separate message that can be sentanytime can be employed for adjusting condition parameters. Thecondition parameters will be described in greater detail below in FIG.7. After receiving a message the serving support node SGSN and themobile station MS perform authentication signalling according to priorart in messages 2-2 (Security functions). When the authentication isperformed the serving support node SGSN sends a create PDP-contextrequest (CreatePDPContextRequest) to the multimedia message servicecentre MMSC in message 2-3, to which the service centre replies bysending a create PDP-context response (CreatePDPContextResponse) to theserving support node in message 2-4. The serving support node SGSNtransmits an acceptance to the mobile station MS by sending an activatePDP-context acceptance (ActivePDPContextAccept) in message 2-5. Afterthis the context to the multimedia message service centre MMSC isactivated from the mobile station, and the mobile station can send andreceive multimedia messages through the multimedia message servicecentre.

The multimedia service context activation shown in FIG. 2 may occuralways when the mobile station makes attach to the GPRS network, thesignalling in FIG. 2 then being a part of network attachment signalling.Alternatively the user may activate the multimedia service context whendesired or activation may occur as a consequence of an activationrequest received from the GPRS network (GPRS network requestedPDP-context activation). The activation request can be generated by, forexample, a multimedia message service centre, if it observes that themessage has to be delivered to such a mobile station that has notactivated the MMS-context. If the mobile station activates theMMS-context always when it makes attach to the network, the multimediamessage service centre MMSC is automatically informed about the mobilestation being in the network again, and a separate “alarm system” likethe one implemented in connection with short message service is notnecessarily needed.

In an embodiment where the multimedia message is transferred along acircuit-switched route or through the conventional GSM network, theMMS-context does not necessarily have to be activated.

In a third preferred embodiment of the invention the MMS-context iscreated through the GGSN node, in which the PDP-context has to beactivated in accordance with prior art. Then the MMS-context does nothave to be activated.

FIG. 3 shows signalling according to a protocol needed for transferringa multimedia message in the first preferred embodiment. A specificprotocol is needed for transferring multimedia messages between themultimedia message service centre and the mobile station. The protocolis overlying the actual transmission protocols. For example, in themobile station MS the protocol overlies the SNDCP protocol and the GTPprotocol in the multimedia message service centre MMSC. It is assumed inthe example shown in FIG. 3 that the MMS-context in the receiving mobilestation is activated. Since the MMS-context is activated, the multimediamessage service centre MMSC comprises up-to-date routing information,because the SGSN informs the MMSC as “other” gateway support nodes GGSNabout the movements of the user by sending a PDP-context update request(Update PDP-context Request). It is also assumed that direct deliveryconditions are met and the multimedia message is delivered. Theconditions are described in greater detail in FIG. 7.

With reference to FIG. 3 a multimedia message has arrived to themultimedia message service centre MMSC. The sender of the message haspreferably sent the message directly using an MSISDN telephone number.If the message is sent from another mobile station, then the address ofthe recipient is only the MSISDN telephone number. If the message issent by means of an application in, for example, the Internet orIntranet, the address of the recipient can be written, for example, asMSISDN@operator.country or first name.last name@operator.country.However, using the address of the latter example requires that themultimedia message service centre has a connection to a domain nameserver. The recipient can also be indicated in some other way separatelyagreed upon. When the multimedia message service centre MMSC hasestablished the location of the mobile station corresponding to theaddress it sends through the serving support node SGSN to the mobilestation MS the contents of the message or if the message is so long thatis must be divided into segments the first segment thereof in message3-1 multimedia message delivery (MMSDeliver). The message is transferredin the first preferred embodiment preferably using the GTP protocolbetween the MMSC and the SGSN and using the SNDCP protocol between theSGSN and the MS. Message 3-1 multimedia message delivery preferablyincludes the following elements: a parameter showing that a reply pathexists; a message reference; a segment number; whether a last segment isconcerned; an address of the message sender; a parameter indicating howthe user data or the actual contents of the message are coded; a servicecentre time stamp indicating the time when the service centre received amessage and user data. Message 3-1 may also include the size of theactual multimedia message (particularly if it is divided into severalsegments). The MS can use this information, for example, when decidingwhether it has enough memory available for the message. This is usefulparticularly in the embodiments where a separate context is not createdor where the messages are automatically sent to the user. In addition,the message may comprise a parameter indicating what the user data is.By means of said parameters the mobile station identifies whether itreceived text, video images, ordinary images, speech or a combinationthereof in the message. The user data type can also be concluded fromthe coding used. The reply path comprises a reply routine used inconnection with multimedia messages. By means of the reply path thereply sent by the subscriber is routed to the mobile station that sentthe message, through the multimedia message service centre through whichthe message was originally delivered to the subscriber, instead of themultimedia message service centre stored as a default value in theterminal. Said routine allows the subscriber to reply to the multimediamessage without having to know the network address of the multimediaentity or the multimedia message service centre that originally sent themessage. The reply does not have to be of the same type, as a textmessage can be sent as a reply to an image message.

When the mobile station has received message 3-1, it sends anacknowledgement in message 3-2 (MMSDeliverAck) which preferably includesthe reference and segment number of the received message. Message 3-2 issent from the mobile station to the serving support node SGSN using theSNDCP protocol and using the GRP protocol between the serving supportnode and the multimedia message service centre. Message pairs 3-1 and3-2 are sent until the last segment of the message has been delivered.One acknowledgement message 3-2 can be used to acknowledge one or moremessages 3-1. In the embodiment that least loads the network, the mobilestation awaits until it has received all segments belonging to the samemultimedia message, and acknowledges the entire message with a singleacknowledgement. When the entire message is acknowledged, the multimediamessage service centre can, for example, form a billing recordconcerning the sending of the message and acknowledge the delivery ofthe message from the message sender.

When the mobile station has received the multimedia message, it storesit in the memory and informs the mobile station user about the receivedmultimedia message or triggers a predetermined application. At the sametime the mobile station preferably indicates the type and size of themessage. If the multimedia message is sent in several segments, themobile station identifies the symbol of the last segment and is able tocompose the message. The user “reads” the message when it suits him/her.The mobile station can also deliver a multimedia message or a messagethereof to an external terminal attending to the following measures.

Message 3-2 can also be a negative acknowledgement (MMSDeliverNack), forexample, if the mobile station does not have enough memory available.Alternatively the mobile station can send an explicit negativeacknowledgement message.

In a second preferred embodiment where multimedia messages are deliveredthrough an ordinary short message service, messages are transferred asshort message signalling messages over the radio interface using an LLCprotocol.

In the embodiments, where a separate context is not activated at all orwhere the MMS-context is not always activated when the mobile stationcan be reached, the MMSC must retrieve routing instructions from therelevant home location register HLR in order to know where to sendmessages 3-1 and 3-2 in FIG. 3. Furthermore, in the embodiments, wherethe MMS-context is not always activated when the mobile station can bereached, the multimedia message service centre can, for example, send acontext activation request (Network Requested Context Activation) to themobile station after receiving routing instructions. After the receptionof the context activation request the mobile station activates theMMS-context as shown in FIG. 2. Alternatively a short message can besent to the mobile station to inform about the reception of themultimedia message. The user then decides when he/she wishes to receivethe message and initiate the MMS-context activation.

If the multimedia message cannot be delivered to the mobile stationbecause e.g. the radio channel circumstances are poor or the mobilestation has logged out from the network, then the process may proceed asa short message service. However, the multimedia message service centreis informed about failure and the message is stored for retransmission.If the embodiment requires an “alarm system”, the home location registerHLR is informed about a waiting multimedia message. The HLR updates thedata needed in the register informing that a multimedia message iswaiting for this subscriber in the multimedia message service centre.When the mobile station next makes the GPRS attach the home locationregister HLR informs the multimedia message service centre about it,which in turn delivers the message as explained above in FIG. 3 assumingthat the validity period of the message is still valid. The multimediamessage service centre MMSC deletes outdated messages from its memory.

FIG. 4 shows signalling according to a protocol needed for transferringa multimedia message in the first preferred embodiment when one of thedirect delivery conditions is not fulfilled. The conditions areexplained in greater detail in FIG. 7. The multimedia message istherefore not delivered directly to a mobile station, but a shortmessage can preferably be sent to the mobile station informing about awaiting multimedia message. It is assumed in the example in FIG. 4 thatthe MMS-context is activated. It is also assumed that the multimediamessage can be delivered and that the validity period of the multimediamessage is still valid.

With reference to FIG. 4, a multimedia message has arrived to themultimedia message service centre MMSC, and the recipient of themultimedia message must be informed about the reception of themultimedia message, which cannot automatically be forwarded. In thefirst preferred embodiment the multimedia message service centre issuesa command to the short message service centre SMSC to generate and senda short message to the mobile station MS in message 4-1 deliver(Deliver). The message includes the telephone number of the recipientMSISDN, the address APN of the multimedia message service centre MMSC,the multimedia message identifier and preferably the multimedia messagesize. The message may include other data as well, such as an indicationof the content type of the multimedia message. The more information canbe added from the multimedia message to the short message, the betterthe recipient is able to conclude when he/she wants to receive themessage. However, it is essential that the data in message 4-1 enablesthe short message service centre to know to whom it sends the shortmessage and from which multimedia message service centre it has receivedthe command. When the short message service centre SMSC has receivedmessage 4-1 it generates the short message, in which the multimediamessage service centre is indicated as a sender address and themultimedia message identifier is indicated as a message identifier.Alternatively the MMSC can generate the short message, in which case itis included in message 4-1. When a short message is in the short messageservice centre SMSC, the SMSC studies the address of the recipient andrequests a routing address (Send Routing Info For SMS) from the relevanthome location register in message 4-2 on the basis of the subscriber'sMSISDN telephone number. The home location register sends normal routinginstructions for short messages to the short message service centre inmessage 4-3 (Send Routing Info For SMS Ack) including either the addressof the support node SGSN serving the mobile station or the address ofthe mobile switching centre MSC serving the mobile station or both. Theshort message service centre SMSC delivers the short message to themobile station in message 4-4 (SM delivery) in accordance with prior artthrough the mobile switching centre MSC or the serving support nodeSGSN.

When the mobile station user decides to load a multimedia message sentfor him/her into the mobile station, he/she issues a command to themobile station to load the multimedia message. The mobile station sendsthrough the support node SGSN serving the mobile station to the addressof the multimedia message service centre in the short message informingabout the multimedia message a multimedia service request (MMSRequest)in message 4-5, where the multimedia message identifier in the shortmessage is a parameter. In the first preferred embodiment the message ispreferably transferred using the SNDCP protocol between the MS and theSGSN and using the GTP protocol between the SGSN and the MMSC. When themultimedia message service centre MMSC has received message 4-5 italready knows the routing information of the mobile station, since itreceived the message from the serving support node SGSN. Hence, themultimedia message service centre retrieves from its memory a multimediamessage according to the identifier in message 4-5. When the multimediamessage service centre MMSC has found the message it sends to the mobilestation MS through the serving support node SGSN the contents of themessage or if the message is so long that it has to be divided intosegments the first segment thereof in message 4-6 multimedia messagedelivery (MMSDeliver). Message 4-6 corresponds to message 3-1 shown inFIG. 3. When the mobile station has received message 4-6 it sends anacknowledgement (MMSDeliverAck) in message 4-7. Message 4-7 correspondsto message 3-2 shown in FIG. 3. Sending the actual message andacknowledging transmission are similar irrespective of whether themultimedia message was sent directly to the mobile station or whether ashort message was sent to inform about the multimedia message. Amultimedia message divided into segments is delivered using messagepairs 4-6 and 4-7 as explained in FIG. 3. When the message has beendelivered, the mobile station informs the user about the receivedmessage as shown in FIG. 3.

If a short message is not sent to the user when a multimedia messagearrives (for example, an operator does not support the feature, the userdoes not want a short message to be sent or wants a short message sentonly for the first multimedia message waiting) the user may be offered aspecific operation (MMS Status Request) for the inquiry of attributes ofmultimedia messages waiting in the multimedia message service centreMMSC. When the user is informed about waiting multimedia messages andthe identifiers thereof (MMS Status Response) he/she may retrieve onlythe messages he/she desires from the multimedia message service centre.

If the life time, or validity time, of the multimedia message is nolonger valid, the multimedia message service centre preferably informsthe mobile station that the message can no longer be delivered.

In embodiments, where the MMS-context is not always activated when themobile station can be reached, the mobile station can, for example, bearranged to trigger the MMS-context activation as a response to theuser's command to load the multimedia message as shown in FIG. 2. Themultimedia message service centre can also send a multimedia servicerequest after receiving the MMS-context activation request to the mobilestation, and after the reception thereof the mobile station activatesthe MMS-context as shown in FIG. 2.

In some preferred embodiments of the invention an identifier of themultimedia message recipient is also attached to message 4-1. The personwho possesses the recipient identifier is the correct recipient of themessage. The recipient identifier is preferably a cryptographicidentifier, for example a hash, in which the elements may include thesender of the multimedia message (for instance, MSISDN), the recipient(for instance, MSISDN), the contents and a consecutive number. Theelements preferably also include the contents of message 4-1 and anMMSC-specific secret value. The created recipient identifier can obtainany value which, however, remains the same when the value is calculatedusing the same element values. If the value of one element changes, thenthe hash “unexpectedly” changes in such a manner that a new hash cannotbe calculated from the old one. This recipient identifier is transmittedin message 4-4 to the mobile station user, who employs the recipientidentifier in message 4-5 to identify the multimedia message to bereceived and the correct recipient. Other authentications are not neededin these embodiments.

FIG. 5 shows signalling according to a protocol needed for transferringa multimedia message in the first preferred embodiment, when the mobilestation wishes to send a multimedia message. The mobile station can, ifnecessary, divide the message into segments, if the message is so largethat it cannot be transferred over the radio interface in one message.The mobile station sends through the serving support node SGSN to themultimedia message service centre MMSC the contents of the message or,if the message is so long that it has to be divided into segments thefirst segment thereof in message 5-1 multimedia message delivery (MMSSubmit). The message is preferably transferred using the SNDCP protocolbetween the mobile station MS and the serving support node SGSN andusing the GTP protocol between the SGSN and the multimedia messageservice centre MMSC. Message 5-1 the multimedia message deliverypreferably comprises the following parts: a parameter indicating that areply path is requested, a message reference, a segment number, whethera last segment is concerned, a destination address of the message, aparameter indicating how the user data, or the actual contents of themessage are coded, a validity period of the message indicting when themessage is no longer delivered to the recipient and user data. Inaddition, message 5-1 may include a parameter indicating what user datais. By means of said parameter the multimedia message service centreidentifies whether it has received text, video images, ordinary images,speech or a combination thereof, and can correspondingly inform therecipient. From the coding information the multimedia message servicecentre may also conclude the same information. If the multimedia messageis intended for another mobile station user, the MSISDN telephone numberof the recipient is preferably used as the destination address. The IPaddress according to the Internet technique or the form first name.lastname@x.y.z can be used as the destination addresses of other recipients.However, the use of the latter alternative requires that the multimediamessage service centre communicates with a domain name server enablingthe change of a logical name into an IP address.

When the multimedia message service centre MMSC has received message5-1, it sends an acknowledgement (MMS Submit Ack) in message 5-2,preferably comprising the reference and segment number of the receivedmessage. Message 5-2 is sent using the GTP protocol between themultimedia message service centre and the serving support node and usingthe SNDCP protocol from the serving support node SGSN to the mobilestation MS. Message pairs 5-1 and 5-2 are transmitted until the lastsegment of the message has been sent. The message pairs canalternatively be replaced with the acknowledgement mechanisms describedin FIG. 3. Thereafter the multimedia message service centre can send amessage to the recipient as shown in FIG. 3 or 4, for example. Message5-2 can also be a negative acknowledgement (MMS Submit Nack).

The signalling messages shown above in FIGS. 2, 3, 4 and 5 are onlypresented by way of an example and may include several separate messagesfor transmitting the same information. The messages may also compriseother information, and be freely combined. The message names can alsochange. Depending on the operator and system other network elements,into which different functionalities are spread, can also participate indata transmission and signalling. There is no need for all networkelements shown in the Figure to participate in signalling, if themessage is, for example, delivered through another route to the mobilestation MS.

In a third preferred embodiment the signalling shown above in FIGS. 3, 4and 5 is performed in such a manner that the SGSN transmits the messagesto the gateway support node GGSN preferably using the GTP protocol,which in turn transmits the messages preferably using the IP protocol tothe multimedia message service centre MMSC. In the third preferredembodiment the short message service gateway SMSGW is not utilized, butinstead of a short message the multimedia message service centre MMSCsends a small information message as a multimedia message or datamessage to the recipient. Alternatively the MMSC can issue a command tothe GPRS gateway support node GGSN to inform about the multimediamessage in some other way.

FIG. 6 shows the operation of the multimedia message service centre inthe first preferred embodiment, where it is assumed that the MMS-contextis activated. It is also assumed that the changing conditions and theconditions set by the operator are determined to the multimedia messageservice centre. Here the conditions refer to conditions that amultimedia message fulfils and can therefore be sent directly to therecipient. Such conditions may include message size, type of messagecontents, user interface of the recipient's mobile station, codingssupported by the mobile station and content type supported by the mobilestation user interface, for example the invention does not restrict thenumber of conditions. The conditions are also described in FIG. 7. It isalso assumed that if the first segment of the message can be delivered,the entire message can be delivered.

FIG. 6 starts from a situation where the multimedia message servicecentre has received a multimedia message to be sent to the mobilestation MS in step 600. In step 601 the MSISDN telephone number of therecipient is distinguished from the message and the conditionsassociated with the telephone number and the general conditionsdetermined by the operator are searched for in step 602. In step 603 thevalues according to the conditions, such as the message size and type,are distinguished from the message. In step 604 it is checked whetherthese values and the conditions determined by the operator andassociated with the telephone number are fulfilled. If the conditionsare met, the multimedia message can be directly sent to the mobilestation, and the message is therefore routed in step 605. The routinghas been explained in more detail in FIG. 3. Then, in step 607, it ischecked whether the message is so large that it must be divided intosegments, i.e. if the message has to be divided. The division must beperformed since the SNDCP and GTP protocols of the GPRS network cannottransfer messages exceeding 1500 bytes. If the message has to bedivided, it is segmented in step 608. In segmentation the message isdivided into segments, which are numbered and the last segment ismarked. When the message has been divided, a first segment is sent instep 609 and an acknowledgement is received in step 610. Segments canalso be sent gradually as the message is being segmented. If it is notedin step 611 that the acknowledgement is positive, that is the segmenthas been delivered, the next segment is sent in step 612, and thepositive acknowledgement of which is received in step 613. Then, in step614, it is checked whether any segments remain. If segments are found,the process proceeds to step 612 and sends the next segment. The loopformed of steps 612, 613 and 614 is repeated until all segments aresent. Then, the process proceeds to step 615, where it is noted that themessage is sent and an acknowledgement is possibly sent to the sender ofthe message. In addition, a billing record is formed or the necessarydata is sent to the billing centre. This solution provides the advantagethat depending on the contract either the sender or the recipient orboth can be billed. The problem of prior art voice messages can thus beavoided. The problem is that both parties always have to pay, the senderwhen sending the message and the recipient when receiving the message.

If it is noted in step 611 that the received acknowledgement is notpositive, then the process proceeds to step 616 where the message isstored into the memory for retransmission, if the mobile station makesattach to the network during the validity period of the message.Processing the message in step 616 can also depend on the reasonindicated in the negative acknowledgement. For example, if the user doesnot want to or is not able to receive the message when it is sent, thenthe message is stored in the memory. Possible reasons why a user doesnot want to or is not able to receive messages are, for example, theinadequacy of the memory, the message type, the long transmission timeof the message or the sender identification data. Such a situation mayarise, for example, because the conditions determined in the MMSC areinadequate or because the message is always automatically sent in theembodiment employed. The user can also indicate that he/she does notwant to receive the message in the future, in which case the message isdeleted from the memory, if it has been stored therein.

If it is noted in step 607 that the message does not have to be divided,the last segment is then indicated as the message segment in step 617,whereafter the message is sent in step 618 and acknowledged in step 619.If it is observed in step 620 that the acknowledgement is positive, i.e.the segment has been delivered, the process proceeds to step 615, whereit is noted that the message has been sent and an acknowledgement ispossibly sent to the sender of the message. If it is observed in step620 that the received acknowledgement is not positive, the processproceeds to step 616, where the message is processed as shown above.

If it is observed in step 604 that one of the conditions is notfulfilled, then the message cannot be directly sent to a mobile station.Instead a short message informing the mobile station about a multimediamessage is sent in step 621 through the short message service centreSMSC. In step 622 the multimedia message is stored into the memory towait for delivery. In step 623 a message request is received from themobile station and the requested message is retrieved from the memory instep 624. Then the process proceeds to step 607 to check if the messagemust be divided, and thereafter the process proceeds as shown above.

The multimedia messages stored in the memory are deleted from the memoryif the validity period thereof is no longer valid or if the multimediamessages are transmitted successfully to the recipient. If the requestin step 623 is received when the validity period of the multimediamessage has elapsed, then the message can naturally not be found in thememory, and the mobile station is preferably informed that the messagecannot be delivered because the validity period thereof is no longervalid.

If the first segment of the message can be delivered but another segmentcannot be delivered, then the entire message is stored in the memory forretransmission.

The steps presented above in FIG. 6 are not shown in an absolutelychronological order and a part of the steps can be performedsimultaneously or in a deviating order. Other operations can beperformed between the steps. Some of the steps can be left out, forexample, the acknowledgement of the message is checked only after thesegments have been sent. An example of a step that can be left out isstep 602 in which conditions are searched for when all messages includethe same condition or conditions.

In a preferred embodiment of the invention the multimedia messageservice centre can change the coding of the multimedia message to acoding that the receiving mobile station supports, or to an otherwisemore optimized form of transmission or presentation. For example, amessage coded by mpeg-coding can be released in the multimedia messageservice centre and recoded by jpeg-coding. These measures are preferablyperformed before the check in step 607. In another preferred embodimentof the invention the multimedia message service centre can pack themessages exceeding a particular limit size, if they are not packedalready. This measure is preferably performed before the check in step607.

The invention does not require restricting the multimedia message size.However, at times the operator or the recipient wishes to restrict themessage size. It is then checked in the flow chart shown in FIG. 6, forexample after step 602, if the multimedia message is too large. If it isnot, the process proceeds as shown in the Figure. If it is, themultimedia message is not delivered to the recipient. Then the sendercan be informed that the message cannot be delivered due to theextensive size thereof.

A value of the recipient identifier can be calculated before step 621and then sent to the mobile station in the embodiments that employ aseparate recipient identifier, like a hash. In addition to themultimedia message an identifier can be stored in these embodiments instep 622. Then in step 623 the received message comprises a separatevalue for the recipient identifier, on the basis of which the correctmultimedia message is retrieved in step 624.

It is assumed in FIGS. 2–6 above that a multimedia message is alwayssent as packet-data. In some embodiments it may also be sent ascircuit-switched data through the mobile switching centre MSC. Atpresent this solution requires that the user has a separate MSISDNtelephone number for data calls, but according to what is currentlyknown the situation will change in such a manner that a separatetelephone number for transmitting data will no longer be needed. When amultimedia message is to be sent in circuit-switched and when indata-switched mode can be decided on the basis of the conditions set bythe operator or the conditions that can be changed by the user.Furthermore, some embodiments allow an attempt to be made to transfer amultimedia message intended to be transferred as packet-data ascircuit-switched data, if the transmission as packet-data is notsuccessful. The transmission mode can also be selected in someembodiments. For example, a small multimedia message including text canbe sent as a packet-switched message to the recipient, whereas a largemultimedia message including video images and speech can be sent incircuit-switched mode. A multimedia message can also be sent asconcatenated short messages.

FIG. 7 illustrates a multimedia message service centre and the essentialoperations thereof regarding the invention. FIG. 7 is a block diagramshowing a multimedia message service centre MMSC of the invention. Themultimedia message service centre MMSC comprises an interface part L1for receiving and sending short messages to and from the mobile stationof the mobile communications system. Depending on the embodiment theinterface part L1 transmits the message through an intra-operatorbackbone network and a serving support node, and through a short messageservice centre or a backbone network and a gateway support node. Themultimedia message service centre MMSC may comprise interface parts L2(only one shown in the Figure) for connecting a short message servicecentre to other networks, such as the Internet, another data networkand/or a public switched telephone network. These interface parts allowmultimedia messages to be sent and received. In addition to these theshort message service centre comprises an application part APtransferring the multimedia message received by the multimedia messageservice centre MMSC to be forwarded as shown, for example, in FIG. 6.

The application part AP identifies the signalling messages shown inFIGS. 2, 3 and 4 and knows how to send and receive messages. Theinterface parts attend to interpreting lower level protocols. Inaddition, the application part AP stores a multimedia message, whichcould not be delivered, into its memory M and retrieves it therefrom,when the multimedia message has successfully been delivered or when themobile station requests the delivery of the multimedia message. Theapplication part attends to the fact that the multimedia messages ormultimedia message segments sent to the mobile station include at leastthe parts determined in FIGS. 3 and 4. The application part can segmentthe messages, or divide them into segments, as shown in FIG. 6 in such amanner that the multimedia message size does not exceed the largest sizeallowed of the messages transmitted in the network and at the airinterface. Correspondingly the application part can compose an entiremultimedia message from the received segments for further delivery. Theapplication part AP can be arranged not to compose an entire multimediamessage of the received segments, if the recipient of the message isanother mobile station in the same mobile communications system.However, in such an embodiment the application part AP can calculate thesize of the message in segments. The application part AP also attends tothe fact that the multimedia messages whose validity period ends aredeleted from the memory, for example, by indicating the memory areaallocated for the message as a free area. The deleted message can remainin the memory until a new message is written over it. The applicationpart can no longer find out the contents of the deleted message. Theapplication part can be arranged to add a validity period to messageslacking it. The application part AP can also be arranged to checkwhether the MMS-context is activated and to generate the MMS-contextactivation request to the mobile station MS.

The application part AP may comprise permanent conditions concerning allmultimedia message deliveries allowing the application part to directlyfilter the messages to be sent from the messages that must be informed.The permanent conditions can be located in the memory M. The applicationpart AP can also be arranged to retrieve from the memory Msubscriber-specific conditions concerning the multimedia messagedeliveries and permanent conditions possibly located therein. Theapplication part AP can also be arranged to inquire aboutsubscriber-specific conditions from the home location register, if theyare maintained therein. The application part AP can also be arranged todistinguish values concerning the conditions from the multimedia messageand to check whether the conditions are fulfilled. If the conditions aremet, the application part is arranged to send the multimedia messagedirectly to the mobile station. Permanent conditions refer to conditionsset by the operator, and which are identical for all messages.Subscriber-specific conditions refer to conditions set for eachsubscriber, and to which a terminal, a subscriber or an operator canprovide limiting values. If the embodiment supports subscriber-specificconditions, then the application part AP is arranged to update theconditions. The permanent conditions are preferably updated through thenetwork management system.

The multimedia message size and type can, for example, be used aspermanent conditions. If, for example, the multimedia message sizeexceeds the size determined in the conditions, the multimedia messagewill not be delivered directly. Even if the multimedia message size issmaller than what is determined in the conditions in the example, butthe contents are not the same as determined in the conditions, then themultimedia message is not delivered directly.

Subscriber-specific conditions may include a coding mode supported bythe terminal, a content type supported by the terminal, the amount ofavailable memory in the terminal, the priority of the multimedia messageetc. In the MMS-context activation the terminal can indicate codingmodes and the amount of available memory, in which case the applicationpart AP updates these values to correspond with the values of thecorresponding conditions. The subscriber can update the specificconditions thereof, such as the size of the multimedia message to besent directly, for example by using a WWW interface or a signallingmessage. The operator may in turn determine a condition for somesubscribers, on the basis of which the text message having the largestpriority must be sent directly irrespective of the size. The applicationpart is arranged, when checking the last condition, to “skip” thecontradicting conditions. The conditions can thus be of differentlevels. When setting conditions logical operators such as AND, OR, XOR,NOT can also be employed. The invention does not in any way restrict theconditions, or how they are formed or applied, but they can freely beplanned by the operator.

In embodiments where alternative delivery routes can be selected for themultimedia message, the application part AP is arranged to select thedelivery route based on the given route conditions, and to request forrouting instructions for said delivery route. The route condition can,for example, be the following: text messages smaller than size Xconcatenated as short messages, messages including video images andexceeding size Y in circuit-switched mode, others in packet-switchedmode.

In the embodiments employing a separate recipient identifier, like ahash, the application part AP is arranged to calculate or to allocate inanother way the recipient identifier and to add it to the messageinforming about the multimedia message. In these embodiments theapplication part is arranged to retrieve the multimedia message from thememory on the basis of the recipient identifier.

The multimedia message service centre can also comprise a generatingpart GP of the message for generating short messages for example inaccordance with the instructions provided by the application part.Depending on the embodiments the generating part GP can also transmit acommand to the short message service centre to generate a short message.In the embodiments where short messages are not used, the generatingpart can generate a data message or a small multimedia message informingabout a multimedia message waiting for a delivery request.

The multimedia message service centre may also comprise a packaging partPP that checks whether the contents of the multimedia message arealready packed. If the contents are not packed, the packaging part PPperforms the packaging. Data is thus transferred more efficiently, asthe amount to be transferred is reduced. The packaging part preferablychecks, for example, through the application part whether packedmessages can be sent to the mobile station. The packaging part PP canalso unpack the packed contents of the received multimedia message, ifpacked messages cannot be sent to the mobile station.

The multimedia message service centre may also comprise a codingconversion part CCP. The conversion part releases the message codingsand codes messages according to instructions provided by the applicationpart. If, for example, a text is coded by ASCII8 coding, but the mobilestation supports ASCII7 coding only, the conversion part converts theASCII8 coding to ASCII7 coding. The message can thus be delivered to themobile station in such a manner that the contents thereof remainunchanged and that the message can still be read.

The interfaces located in the interface parts L1, L2 in the multimediamessages service centre are the application interfaces needed in thefirst preferred embodiment for the data networks such as the IPinterface for the Internet or Intranet the interface implemented, forinstance, using the protocol shown in FIGS. 3, 4 and 5 for the mobilestation MS, the MAP/SS7 interface or the home location register HLR, theGTP/IP interface for the serving support node SGSN and, for example, theCIMD interface for the short message service centre. In addition aninterface is needed for the billing gateway centre preferably forbilling the sender of sent messages. Possible interfaces also include aninterface for the domain name server and an interface for the publicswitching telephone network. The latter is needed if a multimediamessage is loaded as circuit-switched data. An interface is not neededfor the serving support node in the second preferred embodiment of theinvention, since the multimedia messages are sent through a shortmessage service gateway SMSGW. However, an X.25 interface is at leastcurrently needed for the short message service gateway SMSGW. Aninterface is not necessarily needed for the home location register norfor the serving support node SSGN in the third preferred embodiment ofthe invention. The gateway support node GGSB requires an interfacepreferably an IP interface.

The required interfaces can deviate from the above and are dependent onthe protocols supported by the network elements participating in theoperation.

Although FIGS. 3, 4, 5, 6 and 7 show that when certain conditions aremet a multimedia message is sent directly to the recipient, it isobvious for those skilled in the art that the same result is achievedeven if the conditions are set such that their fulfillment will causeindirect transmission.

FIG. 8 illustrates the essential parts of the mobile station and thefunctionalities thereof regarding the invention. In the GSM system andthus also in the GPRS network the mobile station MS consists of anactual terminal and of a subscriber identity module SIM detachablyattached thereto. The subscriber identity module is a smart card placedin the mobile station including, for example, data associated withidentifying the subscriber, such as an international mobile subscriberidentity IMSI number identifying the mobile station subscriber, and acertain amount of memory for storing the short messages received by themobile station. The actual terminal comprises a transceiver Tx/Rxincluding antennas, a user interface UI, a controller CP and a memoryM1, from which a certain amount is allocated for storing multimediamessages in the mobile station of the invention.

The user interface UI generally comprises a keyboard, a display, aloudspeaker and a microphone, which are not shown in FIG. 8. By means ofthe user interface UI the user can compose, send, read, look at and/orlisten to, delete and modify multimedia messages and provide thecontroller CP with other instructions when he/she desires. Oneinstruction is the command to request through the mobile station thedelivery of the multimedia message as shown in FIG. 4. The userinterface preferably attends to the release of the multimedia messagecoding. Through the user interface the user is able to provide thesubscriber-specific conditions described in greater detail in FIG. 7with values.

The controller CP obtains from the user interface, for example, impulsesassociated with the multimedia messages presented above in FIGS. 4 and5. The controller CP preferably informs the mobile station MS user abouta multimedia message that has arrived for the subscriber to the mobilestation through the user interface UI, for example, with a sound signaland a message or symbol appearing on the display. The controller mayinclude into the above indication information about the message size andtype. The controller CP can also provide the mobile station user withsound signals, text instructions or instruction signals associated withthe operation of the mobile station and/or the mobile communicationssystem through the user interface. The controller can also inform anexternal terminal about the multimedia message and the parametersassociated therewith, or it can forward the multimedia message toanother external terminal.

The controller receives and sends multimedia messages, short messagesand signalling/control messages through the transceiver Tx/Rx. Thecontroller is arranged to send and receive the messages shown above inFIGS. 2, 3, 4 and 5, to add necessary parameters and data therein and tointerpret said parameters and data as shown above. What the controllerdoes depends on the embodiments. For example, the controller CP can bearranged to activate the MMS-context always when registering into theGPRS network or merely as a response to the impulse received from thenetwork or the user. When a multimedia message arrives at thetransceiver Tx/Rx, the controller can check before receiving the messagethat memory allocated for multimedia messages is still available. Thecontroller can also check the message type and the coding used thereinto ensure transmission of the multimedia message to the user through theuser interface. This has the advantage that the controller will not invain store a message that it cannot transmit to the user in the memory.The user can receive the message after he/she has changed terminals, ifthe validity period is still valid. After the reception of themultimedia message the controller of the mobile station according to theinvention preferably stores the message in the terminal memory M1. Ifthe multimedia message is sent in several segments, the controllercomposes the segments into one message before storing the message. Insome embodiments the controller CP can be arranged to store a multimediamessage, which the terminal cannot transmit to the user, into the memoryof an identification unit. The controller can also be arranged to askthe user where he/she wishes to store the multimedia message.

The controller can be arranged to distinguish a short message informingabout a multimedia message from other short messages and to compose anindication of the data to the user through the user interface. If someother way is used to inform about the multimedia message, then thecontroller is arranged to transmit the data to the user in accordancewith the indication manner employed.

When multimedia messages are sent from the mobile station the controllerCP segments the message, if needed, and attaches to the message thenecessary parameters which are described in greater detail in FIG. 5.

The controller can be arranged to add conditions, for exampleinformation about codings supported by the user interface, data typesand available memory to the activation messages of the MMS-context. Thecontroller can be arranged to send information on available memory alsoto an acknowledgement message which the controller sends after thereception of the last segment of the multimedia message.

However, it is essential for the mobile station that it can identify amultimedia message and is able to interpret and transmit the message tothe user by employing the correct means.

It is assumed above that a multimedia message is always received by amobile station. This is, however, not always the case. For example, inthe visiting network area it may be more advantageous to retrieve largermultimedia messages via a fixed network through a local Internetoperator. The use of such a fixed network is preferably implementedusing embodiments employing a separate recipient identifier, for examplea hash.

It should be understood that the above description and the drawingsassociated therewith are merely intended to illustrate the presentinvention. The embodiments described above can be combined and theoperations therein can be connected to one another. Different variationsand modifications of the invention will be obvious for those skilled inthe art without deviating from the scope and spirit of the invention setforth in the attached claims.

1. A method for delivering messages between a terminal using wirelessdata transmission in a telecommunications system utilizing wireless datatransmission and a second party, the method comprising: deliveringmessages of at least two different content types through a same messageservice centre, the content types indicating a presentation of themessage contents; determining at least one first condition at themessage service centre, said at least one condition determining at leastone of the following: the content type or types of a message to be sentdirectly, and a maximum size of the message to be sent directly;checking from the message to be delivered to the terminal whether itmeets the first condition; delivering the message directly to theterminal, if it meets the first condition; and informing the terminalabout the message, if it does not meet the first condition, anddelivering the message as a response to a message request concerning themessage.
 2. The method as claimed in claim 1, wherein the messagecontent indicates the presentation of the message contents which caninclude text, speech, images, video images or combinations thereof. 3.The method as claimed in claim 1, further comprising receiving a valueassociated with the first condition from a terminal user in the messageservice centre; and updating said value with a received value.
 4. Themethod as claimed in claim 1, further comprising receiving a terminalproperty as a value associated with the first condition in the messageservice centre; and updating said value with a received value.
 5. Themethod as claimed in claim 1, further comprising adding a recipientidentifier to the message to provide information about the message to besent to the terminal, the identifier enabling identification of therecipient of the message to be received; and delivering the message onlyif the message request includes the recipient identifier associated withthe message.
 6. The method as claimed in claim 1, further comprisingdelivering messages from the message service centre to the terminalusing at least two different delivery routes; determining at least asecond condition at the message service centre; and selecting thedelivery route for the message on the basis of the second condition. 7.The method as claimed in claim 1, further comprising transferring themessage between the terminal and the message service centre in packetsof a particular size; checking before transferring the message whetherit fits into one packet; and if so, transferring the message in onepacket; if the message does not fit into one packet; dividing themessage into segments so that one segment fits into one packet; andtransferring the message in consecutive segments.
 8. The method asclaimed in claim 1, further comprising employing a same protocol for themessages between the terminal and the message service centre.
 9. Themethod as claimed in claim 7, further comprising composing the messageof the received segments.
 10. A wireless telecommunications systemcomprising at least one terminal, the terminal being able to receivemessages of at least a first content type and a second content type, thecontent type indicating the presentation of the message contents; and amessage service centre for transmitting messages of at least the firstcontent type and the second content type between the at least oneterminal and a second party, the message service centre delivering saidmessages to said terminal as messages according to a first protocol,wherein the message service centre is arranged to check beforedelivering the message to the terminal, whether the message meets atleast one predetermined first condition, said at least one conditiondetermining at least one of the following: the content type or types ofa message to be sent directly, and a maximum size of the message to besent directly, and in response to a result of the check, to deliver themessage directly to the terminal or to inform the terminal about themessage and to deliver the message in response to a message requestconcerning the message; and the terminal is arranged to receive anindication about the message, to inform the terminal user about theindication, and to send the message request concerning the message tothe message service centre as a response to instructions received fromthe user.
 11. The system as claimed in claim 10, wherein the terminal isarranged to inform the message service centre about message contentcodings that it supports; and the message service centre is arranged tocheck the coding of the message to be delivered to the terminal, tocompare it to the codings supported by the terminal, and if the terminaldoes not support the message coding, to change the message coding to acoding supported by the terminal.
 12. The system as claimed in claim 10,wherein the system is arranged to transfer the messages in the systembetween the terminal and the message service centre in packets of aparticular size; and the message service centre is arranged to checkbefore a message is delivered to the terminal, whether the message fitsinto one packet, and if the message does not fit into one packet, todivide the message into segments and to deliver the message to theterminal in consecutive segments.
 13. The system as claimed in claim 12,wherein the message service centre is arranged to pack an unpackedmessage with a packaging method supported by the terminal before themessage service centre checks whether the message fits into one packet.14. A message service centre connectable to a wirelesstelecommunications system, the message service centre comprisinginterface means for receiving messages of at least two different contenttypes and for forwarding to a terminal in a telecommunications system,the content types indicating the presentation of the message contents;and application means for selecting the manner of delivery of saidmessages by checking whether the message meets at least onepredetermined condition, said at least one predetermined conditiondetermining at least one of the following: the content type or types ofa message to be sent directly to the terminal, and a maximum size of themessage to be sent directly to the terminal, and in response to a resultof the check, to deliver the message directly to the terminal or toinform the terminal about the message and to deliver the message to theterminal as a response to a message request concerning the message. 15.The message service centre as claimed in claim 14, wherein theapplication means are arranged to deliver said messages addressed to theterminal and to receive the messages received from the terminal using asame protocol.
 16. The message service centre as claimed in claim 14,wherein the application means are arranged: to check before deliveringthe message to the terminal, whether the message fits into one packet,and if the message does not fit into one packet, to divide the messageinto segments and to deliver the message to the terminal in consecutivesegments; and to receive the message from the terminal in consecutivesegments and to deliver the segments to a second terminal of the systemwithout composing a message thereof.
 17. The message service centre asclaimed in claim 14, wherein the application means are arranged toselect a delivery route for each message on the basis of a predeterminedcondition or predetermined conditions.
 18. A mobile station forreceiving messages, the mobile station being configured to determine atleast one condition determining at least one of the following: thecontent type or types of a message to be sent directly to the mobilestation, and a maximum size of the message to be sent directly to themobile station, wherein the content type indicates the presentation ofthe message contents: the mobile station comprising: a user interfacethrough which the mobile station user can receive messages of at least afirst content type and a second content type; and a controller forreceiving messages of at least the first content type and the secondcontent type using a same protocol, wherein the controller is capable ofreceiving an indication concerning a message waiting for delivery,transmitting the indication to the user through the user interface,sending a delivery request of said message in response to a user commandreceived through the user interface, a receiving said message as aresponse to the delivery request, and sending said at least onecondition in response to a user command received through the userinterface.
 19. The mobile station as claimed in claim 18, wherein thecontroller is further capable of receiving the message in consecutivesegments and composing the message of the received segments.
 20. Themobile station as claimed in claim 18, wherein the controller is furthercapable of sending messages of at least the first content type and thesecond content type, checking before sending the message whether it fitsinto one packet; and if so, sending the message in one packet; if themessage does not fit into one packet; dividing the message into segmentsso that one segment fits into one packet; sending the message inconsecutive segments.